From: Petr Baudis <pasky@suse.cz>
To: Adrian May <adrian.alexander.may@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Android needs repo, Chrome needs gclient. Neither work. What does that say about git?
Date: Fri, 20 Nov 2009 12:50:56 +0100 [thread overview]
Message-ID: <20091120115056.GP17748@machine.or.cz> (raw)
In-Reply-To: <65e170e70911200251q2ec5ec87rc37577dddfd3317d@mail.gmail.com>
On Fri, Nov 20, 2009 at 06:51:32PM +0800, Adrian May wrote:
> It doesn't have the kind of triggers you
> need to assert change control either, and these bolt-on scripts are
> just making life messy.
Can you elaborate?
Petr "Pasky" Baudis
next prev parent reply other threads:[~2009-11-20 11:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2d707e8c-2561-470c-beba-c81e16ac441c@k17g2000yqh.googlegroups.com>
2009-11-20 10:51 ` Android needs repo, Chrome needs gclient. Neither work. What does that say about git? Adrian May
2009-11-20 11:31 ` Johannes Schindelin
2009-11-23 4:11 ` Adrian May
2009-11-23 13:58 ` tytso
2009-11-24 3:48 ` Adrian May
2009-11-24 11:29 ` Bob Hazard
2009-11-24 20:45 ` Daniel Barkalow
2009-11-20 11:50 ` Petr Baudis [this message]
2009-11-20 12:46 ` Jakub Narebski
2009-11-20 15:58 ` Clemens Buchacher
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=20091120115056.GP17748@machine.or.cz \
--to=pasky@suse.cz \
--cc=adrian.alexander.may@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.
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).