Ahhh, OK, I hadn't really read that man page. I only read (in an email)
that it'll set things up for you. So again I was using the wrong
commands. <sigh>
On 03/11/14 11:14, Evan Huus wrote:
If you've got git review installed you can just run that instead of
pushing at all. We've got the config set up so it should just do the
right thing.
On Mar 11, 2014, at 11:01 AM, Jeff Morriss <jeff.morriss.ws@xxxxxxxxx
<mailto:jeff.morriss.ws@xxxxxxxxx>> wrote:
On 03/11/14 10:28, B�lint R�czey wrote:
2014-03-11 15:00 GMT+01:00 Martin Mathieson
<martin.r.mathieson@xxxxxxxxxxxxxx
<mailto:martin.r.mathieson@xxxxxxxxxxxxxx>>:
I too am looking forward to seeing this.
On Tue, Mar 11, 2014 at 1:08 PM, Jeff Morriss
<jeff.morriss.ws@xxxxxxxxx <mailto:jeff.morriss.ws@xxxxxxxxx>>
wrote:
On 03/08/14 04:46, Anders Broman wrote:
Pascal Quantin skrev 2014-03-08 09:56:
Le 08/03/2014 09:45, Anders Broman a �crit :
Thanks a million Pascal, I have to try to find the time to get going
with git :-(
Honestly I'd suggest waiting until someone has written the suggested
how-to-use-it guide (on the wiki?).
I would rather consider reading Pro Git. :-)
It is not that long and it is well written.
Yeah, I did. And I've still had several instances where I set up a
new clone and either:
end up with a push that goes nowhere (forgot to run "git config
--add remote.origin.push HEAD:refs/for/master"?)
end up blowing away my clone and starting again because I did
something else wrong
Step-by-step instructions would prevent that kind of thing.
(I think the major problem is that there are quite a number of
commands to run to get it working; you can get a working clone easily
enough but getting pushes working is a-whole-nother matter. I think
my last blow-up was probably caused because I thought "git review -s"
would set everything up for me but then my "git push" went to
oblivion. And, no, I don't intend to ever type something as long as
"git push origin HEAD:refs/for/master" on a regular basis--unless it
can be set up with tab completion :-).)
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx
<mailto:wireshark-dev@xxxxxxxxxxxxx>>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
___________________________________________________________________________
Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe