From: Petr Baudis <pasky@ucw.cz>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
"David S. Miller" <davem@davemloft.net>,
git@vger.kernel.org
Subject: Re: : Networking
Date: Tue, 26 Apr 2005 20:15:54 +0200 [thread overview]
Message-ID: <20050426181554.GA13224@pasky.ji.cz> (raw)
In-Reply-To: <Pine.LNX.4.21.0504261114090.30848-100000@iabervon.org>
Dear diary, on Tue, Apr 26, 2005 at 05:40:08PM CEST, I got a letter
where Daniel Barkalow <barkalow@iabervon.org> told me that...
> On Tue, 26 Apr 2005, Linus Torvalds wrote:
>
> > On Tue, 26 Apr 2005, Andrew Morton wrote:
> > >
> >
> > The only thing you should be a bit careful about is to remember what the
> > "heads" at different points were. In particular, you want to remember
> > where you merged with me last was. I've started tagging my releases with
> > the git tag facility (_not_ the pasky one, but I think pasky will start
> > picking up on that soon enough), so finding a specific release will be
> > easy, but if you ever do a non-release merge you'll just have to tag it
> > yourself.
>
> Your tag system is in the "cogito-0.8" release, plus a pasky-style way of
> keeping track of what tags you have in your repository.
It came in with merge with Linus, but there's no support in the Cogito
toolkit for it whatsoever.
I'm personally unlikely to get any time for doing it (or much anything
else; but this is probably the priority now) until Sunday evening. :-(
> > > d) To generate davem's tree (patch against linus's current tree (ie: patch
> > > against 2.6.12-rc3+linus.patch)):
> > >
> > > git pull git-net
> >
> > Yes. This should have merged the two (assuming "git pull" does what I
> > think it does).
>
> I think git pull only downloads the contents of the repo and saves the new
> head in a separate file. You're left to do the merge yourself, in case
> what you actually wanted to do was just read the patches in the remote
> repo without merging them.
>
> You probably need a "git merge git-net" here, and things will be in the
> state that Linus expects.
Yes. git pull only pulls the stuff, doesn't merge it (that is, unless it
is tracked branch; but I think this isn't the case; this was cleaned up
in cogito-0.8 and cg-pull now always only pulls, cg-update
pulls+merges).
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-04-26 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050425214326.512b006e.davem@davemloft.net>
2005-04-26 7:57 ` : Networking Andrew Morton
2005-04-26 14:59 ` Linus Torvalds
2005-04-26 15:40 ` Daniel Barkalow
2005-04-26 18:15 ` Petr Baudis [this message]
2005-04-26 17:19 ` Jan Harkes
2005-04-26 18:33 ` Petr Baudis
2005-04-26 18:56 ` Andrew Morton
2005-04-26 19:13 ` Linus Torvalds
2005-04-26 19:51 ` Andrew Morton
2005-04-26 20:11 ` Linus Torvalds
2005-04-26 20:35 ` Bram Cohen
2005-04-28 3:55 ` Ryan Anderson
2005-04-28 4:43 ` Daniel Barkalow
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=20050426181554.GA13224@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=akpm@osdl.org \
--cc=barkalow@iabervon.org \
--cc=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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