From: Andreas Ericsson <ae@op5.se>
To: Jan Hudec <bulb@ucw.cz>
Cc: Kristis Makris <kristis.makris@asu.edu>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: Git and tagging hook
Date: Fri, 17 Oct 2008 09:04:52 +0200 [thread overview]
Message-ID: <48F83914.8080508@op5.se> (raw)
In-Reply-To: <20081016201502.GA6362@efreet.light.src>
Jan Hudec wrote:
> As for people replacing their local commits, this is common especially in
> Linux (and Git) development model.
It's common everywhere where projects use peer review.
Results 1 - 50 of about 14,600 for '"PATCH v2" vger.kernel.org'
Results 1 - 50 of about 360,000 for "PATCH v2"
So yes, it is a very common practice and anything interacting with a remote
database based on each commit action will almost certainly be doing something
wrong quite a lot of the time, especially since not all the patch-series end
up being incorporated into a release anyway.
The only sane integration point is the public watering-hole repository used
for the project, and especially the release branch (or the "for-linus" branches
around the world for sub-projects).
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-10-17 7:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 4:45 Git and tagging hook Kristis Makris
2008-10-06 7:17 ` Andreas Ericsson
2008-10-07 17:13 ` Kristis Makris
2008-10-07 17:28 ` Jakub Narebski
2008-10-08 16:47 ` Kristis Makris
2008-10-08 17:40 ` Andreas Ericsson
2008-10-14 17:22 ` Jan Hudec
[not found] ` <20081014172227.GB6931-hYs7FtC5zV+YSD4dQj0czg@public.gmane.org>
2008-10-14 18:03 ` Kristis Makris
2008-10-14 20:49 ` Andreas Ericsson
2008-10-14 21:33 ` Daniel Barkalow
2008-10-16 20:15 ` Jan Hudec
2008-10-17 7:04 ` Andreas Ericsson [this message]
2008-10-06 7:20 ` Andreas Ericsson
2008-10-07 17:30 ` Kristis Makris
2008-10-08 6:12 ` Andreas Ericsson
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=48F83914.8080508@op5.se \
--to=ae@op5.se \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=kristis.makris@asu.edu \
/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).