git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: rhlee <richard@webdezign.co.uk>
To: git@vger.kernel.org
Subject: Re: Working on merged branches whilst seeing current master
Date: Thu, 12 Nov 2009 06:57:42 -0800 (PST)	[thread overview]
Message-ID: <1258037862366-3993313.post@n2.nabble.com> (raw)
In-Reply-To: <20091111215727.GK27518@vidovic>


Thanks for the help Nicolas,

That cleared up the issue a lot for me.


Nicolas Sebrecht-3 wrote:
> 
>>                                      Yes I know I probably should not be
>> working like this. My branches should be wholly independent. But I doing
>> web
>> development not kernel development so there is much less modularity and
>> branches/features have a tendency to creep into one another.
> 
> This should not be the case. Modularity in the release process and the
> development strategy is not tied to "what I am developing". I'm doing
> some web development too and have no difficulty around this point.
> 

Just to clarify. Do you mean that this should not be the case that you get
feature creep in branches or the fact that this happens does interfere with
your release process/development strategy.

Regards,

Richard
-- 
View this message in context: http://n2.nabble.com/Working-on-merged-branches-whilst-seeing-current-master-tp3987667p3993313.html
Sent from the git mailing list archive at Nabble.com.

  parent reply	other threads:[~2009-11-12 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 17:16 Working on merged branches whilst seeing current master rhlee
2009-11-11 21:57 ` Nicolas Sebrecht
2009-11-12 12:48   ` Tim Mazid
2009-11-12 16:49     ` rhlee
2009-11-26 12:45       ` Tim Mazid
2009-11-12 14:57   ` rhlee [this message]
2009-11-12 15:14     ` Nicolas Sebrecht

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=1258037862366-3993313.post@n2.nabble.com \
    --to=richard@webdezign.co.uk \
    --cc=git@vger.kernel.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 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).