All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell Cattelan <cattelan@thebarn.com>
To: Niv Sardi <xaiki@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Russell Cattelan <cattelan@thebarn.com>,
	xfs@oss.sgi.com
Subject: Re: New XFS git tree on oss.sgi.com
Date: Tue, 09 Dec 2008 18:07:13 -0600	[thread overview]
Message-ID: <493F0831.8030405@xfs.org> (raw)
In-Reply-To: <nccvdtthtyi.fsf@itchy.melbourne.sgi.com>

Niv Sardi wrote:
> Russell Cattelan <cattelan@thebarn.com> writes:
>
>   
>> Christoph Hellwig wrote:
>>
>>     
>>> Now that the xfs-dev branch was updated after a while I tried a git pull
>>> an get a useless error message:
>>>
>>>   
>>>       
>> I agree that is a worthless error message and does nothing to really
>> tell you what the problem is.
>>
>> 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.
>>
>>     
>>> hch@bigmac:~/work/xfs-dev$ git-pull You asked me to pull without
>>> telling me which branch you
>>> want to merge with, and 'branch.origin/xfs-dev.merge' in
>>> your configuration file does not tell me either.  Please
>>> name which branch you want to merge on the command line and
>>> try again (e.g. 'git pull <repository> <refspec>').
>>> See git-pull(1) for details on the refspec.
>>>
>>> If you often merge with the same branch, you may want to
>>> configure the following variables in your configuration
>>> file:
>>>
>>>     branch.origin/xfs-dev.remote = <nickname>
>>>     branch.origin/xfs-dev.merge = <remote-ref>
>>>     remote.<nickname>.url = <url>
>>>     remote.<nickname>.fetch = <refspec>
>>>
>>> See git-config(1) for details.
>>>
>>>
>>> Can you please make each of the current branches a proper git tree
>>> that is easy to work with?  Alternatively I'll just completely stop
>>> bothering with the dev tree if it's such a pain in the ass.
>>>       
>
> Please read git documentation.
>   
seriously?! you need to say this?

>    
> You don't want to be pulling xfs-dev into a xfs/master tree, you should
> setup a remote properly and have local branch tracking them.
>   
Ya and this is a non trivial thing to do without proper instructions.

>   
>> of course this would be so damn confusing if somebody would document
>> the procedures someplace?!
>>     
>
>   
>> Hmm I wonder where we could do that.... ohh wait maybe the WIKI!
>>     
>
> http://xfs.org/index.php?title=Main_Page&action=submit
> --> out of captcha images; this shouldn't happen
>   
Ok fixed.
> you can read this:
>   
Sigh ....
Honestly you think ptools info is useful here?

> ------------------------------------------------------------------------
>
>
> if you s/git.melbourne.sgi.com/oss.sgi.com/
>
> Cheers,

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2008-12-10  0:07 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
2008-12-09 22:20               ` Niv Sardi
2008-12-10  0:07                 ` Russell Cattelan [this message]
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=493F0831.8030405@xfs.org \
    --to=cattelan@thebarn.com \
    --cc=hch@infradead.org \
    --cc=xaiki@sgi.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.