git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Working on merged branches whilst seeing current master

From
rhlee <richard@webdezign.co.uk>
Date
Nov 12, 2009, 14:57 UTC
Message-ID
<1258037862366-3993313.post@n2.nabble.com>
In-Reply-To
<20091111215727.GK27518@vidovic>
Thanks for the help Nicolas,
That cleared up the issue a lot for me.
Nicolas Sebrecht-3 wrote:
Show 11 quoted lines
> 
>>                                      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.
Previous: Tim MazidNext: Nicolas Sebrecht
Message 6 of 7 in “Working on merged branches whilst seeing current master”
  1. rhleeNov 11, 2009
  2. Nicolas SebrechtNov 11, 2009
  3. Tim MazidNov 12, 2009
  4. rhleeNov 12, 2009
  5. Tim MazidNov 26, 2009
  6. rhleeNov 12, 2009
  7. Nicolas SebrechtNov 12, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.