From: Samuel Tardieu <sam@rfc1149.net>
To: Andreas Ericsson <ae@op5.se>
Cc: Bill Lear <rael@zopyra.com>, git@vger.kernel.org
Subject: Re: Using the --track option when creating a branch
Date: Thu, 30 Oct 2008 16:04:08 +0100 [thread overview]
Message-ID: <2008-10-30-16-04-08+trackit+sam@rfc1149.net> (raw)
In-Reply-To: <4909CABD.1040708@op5.se>
* Andreas Ericsson <ae@op5.se> [2008-10-30 15:54:53 +0100]
> Correct me if I'm wrong, but wouldn't my suggestion of not trying to
> push (even matching) branches that haven't been updated since we last
> fetched from the remote do exactly the same thing for your particular
> use-case, but without syntax change and all the annoying minor parts
> that it entails?
Not exactly. I often do some work on a branch which does not mandate
a topic branch and have to switch branches to fix a bug for example.
This would continue to push unterminated changes as well.
Typical use case, which happens (to me) quite frequently:
% git checkout master
[start new feature, estimated implementation time 15 minutes]
% git commit -m "Reorganize foobar in previous of xyzzy."
(note that I'm not sure that I will keep it, I'll know that later
when my next commit is ready, maybe in 10 minutes, no need for
a topic branch)
[mail from a customer, "I noticed some strange behaviour here" --
let's fix it]
% git checkout 2.0-beta1-release-candidate
[fix strange behaviour and add new test]
[test locally]
% git commit -m "Fix strange behaviour baz."
% git push
(so that it goes to the buildfarm for QA testing)
Argh, "master" has been pushed as well. Ok, I could have done
% git branch
(because I know I am on the right branch but do not necessarily
remember its full name all the time)
% git push origin 2.0-beta1-release-candidate
or I could have started a topic branch, but I often push 2 or 3
commits at a time instead, the first one being a refactoring of
existing code to ease the subsequent one.
>From what I have seen, people I am working with often have the
same workflow (do not systematically start a topic branch when
in active development mode)
> Define "many". Perhaps as often as 2-3 times per day. Not very often,
> but frequent enough that I definitely want some short sweet way of
> doing it. OTOH, I also find the "rejected" messages annoying, and I
> definitely feel one could do something about them. However, it's my
> birthday today and I plan on being far too drunk/hungover the entire
> weekend for me to take any actions in that direction.
Happy birthday :)
next prev parent reply other threads:[~2008-10-30 15:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 15:23 Using the --track option when creating a branch Bill Lear
2008-10-29 16:25 ` Santi Béjar
2008-10-29 20:33 ` Bill Lear
2008-10-30 5:12 ` Sam Vilain
2008-10-30 12:04 ` Bill Lear
2008-10-30 12:12 ` Bill Lear
2008-10-30 12:25 ` Andreas Ericsson
2008-10-30 13:52 ` Samuel Tardieu
2008-10-30 14:06 ` Andreas Ericsson
2008-10-30 14:23 ` Samuel Tardieu
2008-10-30 14:41 ` Pierre Habouzit
2008-10-30 14:56 ` Samuel Tardieu
2008-10-30 18:00 ` Sam Vilain
2008-10-30 14:54 ` Andreas Ericsson
2008-10-30 15:04 ` Samuel Tardieu [this message]
2008-10-30 15:25 ` Andreas Ericsson
2008-10-30 15:42 ` Bill Lear
2008-10-30 19:13 ` Marc Branchaud
2008-10-30 17:57 ` Sam Vilain
2008-10-30 23:24 ` Jakub Narebski
2008-11-02 4:23 ` Jeff King
2008-10-30 16:44 ` Sam Vilain
2008-10-30 12:41 ` Santi Béjar
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=2008-10-30-16-04-08+trackit+sam@rfc1149.net \
--to=sam@rfc1149.net \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.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;
as well as URLs for NNTP newsgroup(s).