From: Russell Cattelan <cattelan@thebarn.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: New XFS git tree on oss.sgi.com
Date: Tue, 09 Dec 2008 11:12:39 -0600 [thread overview]
Message-ID: <493EA707.3000409@xfs.org> (raw)
In-Reply-To: <20081209165728.GA18536@infradead.org>
Christoph Hellwig wrote:
> On Tue, Dec 09, 2008 at 10:20:04AM -0600, Russell Cattelan wrote:
>
>> The problem is that you have a tracking branch for xfs-dev so git wants
>> to leave your branch untouched
>> until you actually want to update it from the remote branch origin/xfs-dev
>> What you can do is:
>> % git-fetch
>> % git-pull . xfs-dev
>>
>> That will pull the latest xfs-dev stuff into your current branch.
>>
>
> It might. But remember more than a single command to update a
> repository is just a braindead design. Especially if I have to remember
> a branch name. Even CVS got this right..
>
>
Agreed, I'm not going to defend git cmds, frankly I find most of them
confusing
and poorly documented. It seems like the only way to figured this stuff
out is
read as many howto's as possible and then make some swags.
What I did was clone the tree and then have my "master" branch track
origin/xfs-dev
vs origin/master. That way I can just do git-pulls and have an to date
xfs-dev tree.
-Russell
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-12-09 17:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 7:22 New XFS git tree on oss.sgi.com Lachlan McIlroy
2008-11-25 8:16 ` Christoph Hellwig
2008-11-25 14:27 ` Russell Cattelan
2008-11-25 21:42 ` Mark Goodwin
2008-11-26 3:30 ` Christoph Hellwig
2008-11-26 3:36 ` Russell Cattelan
2008-11-26 1:03 ` Lachlan McIlroy
2008-11-26 1:17 ` Timothy Shimmin
2008-11-26 3:26 ` Russell Cattelan
2008-12-03 3:37 ` Niv Sardi
2008-12-09 9:17 ` Christoph Hellwig
2008-12-09 16:20 ` Russell Cattelan
2008-12-09 16:57 ` Christoph Hellwig
2008-12-09 17:12 ` Russell Cattelan [this message]
2008-12-09 22:20 ` Niv Sardi
2008-12-10 0:07 ` Russell Cattelan
2008-12-10 0:46 ` Mark Goodwin
2008-12-10 1:14 ` Niv Sardi
2008-12-10 6:51 ` Christoph Hellwig
2008-11-26 3:30 ` Christoph Hellwig
2008-11-26 1:00 ` Lachlan McIlroy
2008-11-26 2:00 ` Dave Chinner
2008-11-26 3:29 ` Timothy Shimmin
2008-11-26 4:08 ` Dave Chinner
2008-11-26 5:41 ` Timothy Shimmin
2008-12-04 13:26 ` Christoph Hellwig
2008-12-05 3:29 ` Niv Sardi
2008-12-03 3:45 ` Niv Sardi
2008-11-26 3:28 ` Christoph Hellwig
2008-11-25 14:05 ` Christoph Hellwig
2008-11-26 1:11 ` Lachlan McIlroy
2008-11-26 3:27 ` Christoph Hellwig
2008-12-03 3:48 ` Niv Sardi
2008-12-03 13:04 ` Christoph Hellwig
2008-12-03 23:58 ` Niv Sardi
2008-12-04 12:34 ` Christoph Hellwig
2008-11-26 3:40 ` Eric Sandeen
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=493EA707.3000409@xfs.org \
--to=cattelan@thebarn.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/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