From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: GIT workflow
Date: Sun, 10 Nov 2013 18:01:53 +0100 [thread overview]
Message-ID: <527FBC01.5010509@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 547 bytes --]
Hello, all. We've switched to git some time ago, now we should have some
kind of workflow documents. In particular I think of following points:
- Developpers with commit access can create branches as they see fit as
long as it's prefixed by their name and they don't do sth nasty like
storing binary or unrelated files.
- When committing bigger work should we merge or squash? I think that
squash should be possible if developper desires. Is there any reason to
use merges?
- Which commits should we sign? All? Some? Official releases?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next reply other threads:[~2013-11-10 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 17:01 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2013-11-14 13:20 ` GIT workflow Mikko Rantalainen
2013-11-25 18:26 ` Andrey Borzenkov
2013-11-28 6:45 ` Vladimir 'phcoder' Serbinenko
2013-11-28 17:26 ` Andrey Borzenkov
2013-12-03 12:24 ` Colin Watson
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=527FBC01.5010509@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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).