From: Jonathan Nieder <jrnieder@gmail.com>
To: Stefan Beller <stefanbeller@googlemail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Duy Nguyen <pclouds@gmail.com>,
schlotter@users.sourceforge.net, Ralf.Wildenhues@gmx.de,
git@vger.kernel.org
Subject: Re: [PATCH] add warning for depth=0 in git clone.
Date: Tue, 8 Jan 2013 00:14:01 -0800 [thread overview]
Message-ID: <20130108081401.GB5722@elie.Belkin> (raw)
In-Reply-To: <50EBD453.9050101@googlemail.com>
Stefan Beller wrote:
> I am struggling a little with the development process,
> is a sign-off strictly required for git as it is for kernel development?
Yes. Documentation/SubmittingPatches has more hints.
> Signed-off-by: Stefan Beller <stefanbeller@googlemail.com>
>
> This adds a warning and the previous patch adds the documentation.
Thanks for your work on this.
next prev parent reply other threads:[~2013-01-08 8:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 8:07 [PATCH] add warning for depth=0 in git clone Stefan Beller
2013-01-08 8:09 ` Stefan Beller
2013-01-08 8:14 ` Jonathan Nieder [this message]
2013-01-08 8:12 ` Jonathan Nieder
2013-01-09 0:57 ` Duy Nguyen
2013-01-09 2:53 ` On --depth=funny value Junio C Hamano
2013-01-09 4:18 ` Duy Nguyen
2013-01-09 5:19 ` Junio C Hamano
2013-01-09 14:12 ` Duy Nguyen
2013-01-09 14:59 ` Duy Nguyen
2013-01-09 21:38 ` Stefan Beller
2013-01-11 3:30 ` [PATCH 1/2] fetch, upload-pack: add --no-shallow for infinite depth Nguyễn Thái Ngọc Duy
2013-01-11 3:30 ` [PATCH 2/2] upload-pack: fix off-by-one depth calculation in shallow clone Nguyễn Thái Ngọc Duy
2013-01-11 4:26 ` Junio C Hamano
2013-01-11 3:55 ` [PATCH 1/2] fetch, upload-pack: add --no-shallow for infinite depth Junio C Hamano
2013-01-11 9:05 ` [PATCH v2 1/3] fetch: add --unshallow for turning shallow repo into complete one Nguyễn Thái Ngọc Duy
2013-01-11 9:05 ` [PATCH v2 2/3] upload-pack: fix off-by-one depth calculation in shallow clone Nguyễn Thái Ngọc Duy
2013-01-11 9:05 ` [PATCH v2 3/3] fetch: elaborate --depth action Nguyễn Thái Ngọc Duy
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=20130108081401.GB5722@elie.Belkin \
--to=jrnieder@gmail.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=schlotter@users.sourceforge.net \
--cc=stefanbeller@googlemail.com \
/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).