All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Nicolas Pitre <nico@cam.org>, Junio Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: confusion over the new branch and merge config
Date: Fri, 22 Dec 2006 23:40:49 +0100	[thread overview]
Message-ID: <200612222340.50029.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612221609430.18171@xanadu.home>

Nicolas Pitre wrote:
> 
> Could you at least keep me in CC when replying to me please?

I have Cc-ed you and Junio, but somehow message I send to mailing
list loses the Cc:. Perhaps it is time to change news client (KMail),
or upgrade it...

> On Fri, 22 Dec 2006, Jakub Narebski wrote:
> 
>> <opublikowany i wysłany>
> 
> ?

Sorry, it is added (in my locale) when both sending reply via mail,
and to newsgroup (and to git mailing list via GMane NNTP news2mail
interface).


>> Perhaps less confusing, but also less powerfull. Current notation
>> allows for pulling _without need for tracking branches_.
> 
> Is this really a killer feature worth the confusion?
> 
> If you put the repo to pull from on the command line then sure you might 
> not want a tracking branch, but if you go to the trouble of adding a 
> branch.blah.merge config entry then you certainly don't mind having a 
> tracking branch?

I'm not sure. On one hand you have this feature, pulling without tracking
branch (which is nice workflow for one-branch repos at least), on the
other hand the tracking branch tells us the remote, and we can check if
they match. 

On another hand, you can have two remotes which are the same repository
(mirrors for example)... although that would be better solved by allowing
multiple url...
-- 
Jakub Narebski
Poland

  reply	other threads:[~2006-12-22 22:38 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 22:17 confusion over the new branch and merge config Nicolas Pitre
2006-12-21 23:01 ` Junio C Hamano
2006-12-21 23:21   ` Sean
2006-12-22  0:39     ` Junio C Hamano
2006-12-22  0:46     ` Junio C Hamano
2006-12-22  1:01       ` Sean
2006-12-22  8:31       ` Andy Parkins
2006-12-22  7:50   ` Alan Chandler
2006-12-22  8:21     ` Junio C Hamano
2006-12-22  8:39       ` Andy Parkins
2006-12-22 15:25         ` Alan Chandler
2006-12-22 20:49   ` Nicolas Pitre
2006-12-22 21:04     ` Jakub Narebski
2006-12-22 21:20       ` Nicolas Pitre
2006-12-22 22:40         ` Jakub Narebski [this message]
2006-12-22 23:39     ` Junio C Hamano
2006-12-23  3:10       ` Tom Prince
2006-12-23  5:11       ` Nicolas Pitre
2006-12-23  5:12   ` Jeff King
2006-12-23  5:29     ` Nicolas Pitre
2006-12-23  6:15     ` Junio C Hamano
2006-12-23  6:22       ` Shawn Pearce
2006-12-23  6:28       ` Jeff King
2006-12-23  7:11         ` Junio C Hamano
2006-12-23  7:25           ` Jeff King
2006-12-23  9:51       ` Junio C Hamano
2006-12-23 10:40         ` Jakub Narebski
2006-12-23 15:58         ` Johannes Schindelin
2006-12-23 22:48           ` Jakub Narebski
2006-12-24  6:15         ` Jeff King
2006-12-24 20:49         ` Nicolas Pitre
2006-12-26  7:33           ` Jeff King
2007-01-02 14:49         ` Jeff King
2007-01-02 17:32           ` Junio C Hamano
2007-01-02 17:34             ` Jeff King
2007-01-02 20:04               ` Junio C Hamano
2007-01-02 20:30                 ` Jakub Narebski
2007-01-03  0:24                   ` Santi Béjar
2007-01-03 23:02                     ` Jakub Narebski
2007-01-09 15:05                 ` Jeff King
2007-01-09 16:18                   ` Jeff King
2006-12-23  8:31     ` Jakub Narebski
2006-12-22  8:41 ` Andy Parkins
2006-12-22  9:39   ` Lars Hjemli
2006-12-22 15:10     ` Nicolas Pitre

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=200612222340.50029.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=nico@cam.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 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.