|To:||Christoph Hellwig <hch@xxxxxxxxxxxxx>|
|Subject:||Re: New XFS git tree on oss.sgi.com|
|From:||Russell Cattelan <cattelan@xxxxxxxxxxx>|
|Date:||Tue, 09 Dec 2008 11:12:39 -0600|
|References:||<492BA7AD.5080007@xxxxxxx> <20081125081644.GA20644@xxxxxxxxxxxxx> <492C0B3D.3040002@xxxxxxxxxxx> <492CA07F.1030803@xxxxxxx> <492CC201.3080304@xxxxxxx> <ncc3ah6lyiw.fsf@xxxxxxxxxxxxxxxxxxxxxxx> <20081209091725.GA26180@xxxxxxxxxxxxx> <493E9AB4.1050505@xxxxxxx> <20081209165728.GA18536@xxxxxxxxxxxxx>|
|User-agent:||Thunderbird 22.214.171.124 (Macintosh/20070728)|
Christoph Hellwig wrote:
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 isOn 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 untoucheduntil 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..
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.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: New XFS git tree on oss.sgi.com, Christoph Hellwig|
|Next by Date:||Re: [patch 1/5] replace b_fspriv with b_mount, Russell Cattelan|
|Previous by Thread:||Re: New XFS git tree on oss.sgi.com, Christoph Hellwig|
|Next by Thread:||Re: New XFS git tree on oss.sgi.com, Niv Sardi|
|Indexes:||[Date] [Thread] [Top] [All Lists]|