git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Karl Hasselström" <kha@treskal.com>
To: Patrick.Higgins@cexp.com
Cc: git@vger.kernel.org, Catalin Marinas <catalin.marinas@gmail.com>
Subject: Re: git branch diagram
Date: Fri, 18 Apr 2008 08:46:55 +0200	[thread overview]
Message-ID: <20080418064655.GA23209@diana.vm.bytemark.co.uk> (raw)
In-Reply-To: <911589C97062424796D53B625CEC0025E460C3@USCOBRMFA-SE-70.northamerica.cexp.com>

On 2008-04-17 11:00:56 -0600, Patrick.Higgins@cexp.com wrote:

> I read in the stgit docs that developing directly in the master
> branch is discouraged by convention, but I don't really understand
> why. The git tutorial shows work happening directly in master, so I
> wasn't sure if that's a convention that only makes sense for stgit
> or for plain git, too.

It doesn't even make sense for StGit. The documentation on the StGit
homepage that claims this ("As a convention, you should avoid working
in the 'master' branch of a remote project and use it only as a
reference, since it reflects someone else's work.") is simply
horribly, horribly outdated.

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle

  parent reply	other threads:[~2008-04-18  6:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-17 17:00 git branch diagram Patrick.Higgins
2008-04-18  1:38 ` Sitaram Chamarty
2008-04-18  2:29 ` Roman V. Shaposhnik
2008-04-18  6:46 ` Karl Hasselström [this message]
2008-04-18  8:39 ` Fedor Sergeev
2008-04-18 13:07 ` Matt Graham
2008-04-21  0:30 ` Jakub Narebski
2008-04-21 12:48   ` Matt Graham
2008-04-21 13:06     ` Jakub Narebski
2008-04-21 13:07     ` Luciano Rocha

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080418064655.GA23209@diana.vm.bytemark.co.uk \
    --to=kha@treskal.com \
    --cc=Patrick.Higgins@cexp.com \
    --cc=catalin.marinas@gmail.com \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).