From: Rudolf Polzer <divVerent@alientrap.org>
To: Nanako Shiraishi <nanako3@lavabit.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git push --track
Date: Thu, 14 Jan 2010 08:08:13 +0100 [thread overview]
Message-ID: <20100114070812.GD1528@rm.endoftheinternet.org> (raw)
In-Reply-To: <20100114154154.6117@nanako3.lavabit.com>
On Thu, Jan 14, 2010 at 03:41:54PM +0900, Nanako Shiraishi wrote:
> Quoting Rudolf Polzer <divVerent@alientrap.org>
>
> > I'd like a feature to automatically "transform" a non-tracking local
> > branch into a tracking branch on push. A patch to do that is attached.
>
> How well does this take earlier discussions on the same topic into account? For example, did you study the design discussion in
> http://thread.gmane.org/gmane.comp.version-control.git/135325/focus=135390
I don't really think this has much to do with the other. git branch
--will-track still means one needs to know it at branch setup time, and git
pull --remember still means one needs to type way more stuff than with a simple
push --track.
But well, given the discussion here I see the feature is essentially rejected,
and already was rejected a previous time. Will probably forget about this and
make a shell script that does for ME what I want.
Best regards,
Rudolf
next prev parent reply other threads:[~2010-01-14 7:08 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 15:12 [PATCH] git push --track Rudolf Polzer
2010-01-13 15:43 ` Ilari Liusvaara
2010-01-13 15:55 ` Rudolf Polzer
2010-01-13 16:27 ` Ilari Liusvaara
2010-01-13 16:37 ` Matthieu Moy
2010-01-14 5:21 ` Tay Ray Chuan
2010-01-14 7:00 ` Rudolf Polzer
2010-01-14 23:13 ` Junio C Hamano
2010-01-14 7:16 ` Jeff King
2010-01-15 5:47 ` Junio C Hamano
2010-01-15 14:00 ` Rudolf Polzer
2010-01-15 15:45 ` Miles Bader
2010-01-15 18:16 ` Junio C Hamano
2010-01-14 0:28 ` Miles Bader
2010-01-14 0:25 ` Miles Bader
2010-01-14 0:33 ` Johannes Schindelin
2010-01-14 0:36 ` Miles Bader
2010-01-14 0:46 ` Miles Bader
2010-01-14 7:01 ` Rudolf Polzer
2010-01-14 13:44 ` Martin Langhoff
2010-01-14 14:16 ` Johannes Schindelin
2010-01-14 14:25 ` Matthieu Moy
2010-01-14 14:35 ` Martin Langhoff
2010-01-14 15:27 ` Andreas Krey
2010-01-14 1:27 ` Tay Ray Chuan
2010-01-14 1:35 ` Miles Bader
2010-01-14 1:37 ` Tay Ray Chuan
2010-01-14 1:49 ` Miles Bader
2010-01-14 1:58 ` Tay Ray Chuan
2010-01-14 7:03 ` Rudolf Polzer
2010-01-14 23:46 ` Junio C Hamano
2010-01-15 0:30 ` Miles Bader
2010-01-15 18:18 ` Junio C Hamano
2010-01-15 18:54 ` Miles Bader
2010-01-15 13:26 ` Matthieu Moy
2010-01-14 6:41 ` Nanako Shiraishi
2010-01-14 7:08 ` Rudolf Polzer [this message]
2010-01-14 10:31 ` Johannes Schindelin
2010-01-14 22:27 ` Nanako Shiraishi
2010-01-14 23:50 ` Junio C Hamano
2010-01-15 13:44 ` Rudolf Polzer
2010-01-15 14:09 ` Johannes Schindelin
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=20100114070812.GD1528@rm.endoftheinternet.org \
--to=divverent@alientrap.org \
--cc=git@vger.kernel.org \
--cc=nanako3@lavabit.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.