From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Pierre Muller <pierre.muller@ics-cnrs.unistra.fr>, archer@sourceware.org
Subject: Re: [Archer] Re: [Archer] Question about archer branch managment
Date: Sun, 27 Feb 2011 18:28:00 -0000 [thread overview]
Message-ID: <20110227181752.GH2513@adacore.com> (raw)
In-Reply-To: <20110227175003.GA28937@host1.dyn.jankratochvil.net>
> > Hmmm, I thought that
> >
> > $ git push origin archer-tromey-explosion-project
> >
> > would have worked right from the get go...
>
> Really not:
(I don't know if I'm the only one feeling that way, but your style
is insanely compact for my brain - it often takes a long time to
understand what you're trying to say sometimes)
> $ rm -rf 1 2;mkdir 1 2;cd 1;git init;touch f;git add f;git commit -m f f;cd ..;git clone 1 2;cd 2;git checkout -b x;git push origin ;cd ../1;git branch;cd ..
> Switched to a new branch 'x'
> Everything up-to-date
> * master
> but
> $ rm -rf 1 2;mkdir 1 2;cd 1;git init;touch f;git add f;git commit -m f f;cd ..;git clone 1 2;cd 2;git checkout -b x;git push origin x:x;cd ../1;git branch;cd ..
> Switched to a new branch 'x'
> Total 0 (delta 0), reused 0 (delta 0)
> To /tmp/gittest3/1
> * [new branch] x -> x
> * master
> x
I think I didn't express myself clearly. All I was trying to say is
that "x:x" in a "git push" command is equivalent to "x". I wasn't
understanding the reasoning behind the instructions, but maybe I was
missing something, or making the wrong assumption somewhere (I was
assuming that Pierre named both local and remote branches with
the same name).
--
Joel
next prev parent reply other threads:[~2011-02-27 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 11:26 Pierre Muller
2011-02-24 11:32 ` [Archer] " Joel Brobecker
2011-02-27 17:50 ` Jan Kratochvil
2011-02-27 18:28 ` Joel Brobecker [this message]
2011-02-27 18:59 ` [Archer] " Jan Kratochvil
2011-02-27 17:51 ` Jan Kratochvil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110227181752.GH2513@adacore.com \
--to=brobecker@adacore.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).