From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Philip Oakley <philipoakley@iee.org>
Cc: Roberto Tyley <roberto.tyley@gmail.com>,
Stefan Beller <sbeller@google.com>,
Robert Dailey <rcdailey.lists@gmail.com>,
Heiko Voigt <hvoigt@hvoigt.net>,
Jens Lehmann <Jens.Lehmann@web.de>, Git <git@vger.kernel.org>,
Thomas Ferris Nicolaisen <tfnico@gmail.com>,
emma@gitforteams.com
Subject: Re: [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs")
Date: Sat, 23 May 2015 11:06:55 +0200 [thread overview]
Message-ID: <696c665281fa2abd35c519e0947fef98@www.dscho.org> (raw)
In-Reply-To: <BACC0468FBD24DA584507676EC4E6A5A@PhilipOakley>
Hi Philip,
On 2015-05-22 23:35, Philip Oakley wrote:
> Do I read you right.. That it's necessary to create a PR on git/git
> before submitGit can be used.
Yep.
> And that if I already have a PR which goes back to an alternate fork
> (e.g. my example), then I must move or duplicate that PR onto git/git
> before it can be used.
Yep, the rationale being that you most likely have to rebase your PR to git/git's `master` branch, anyway.
Ciao,
Dscho
next prev parent reply other threads:[~2015-05-23 9:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 8:33 [Announce] submitGit for patch submission (was "Diffing submodule does not yield complete logs") Roberto Tyley
2015-05-22 9:42 ` Johannes Schindelin
2015-05-22 14:41 ` Johannes Schindelin
2015-05-22 17:14 ` Philip Oakley
2015-05-22 19:58 ` Johannes Schindelin
2015-05-22 21:35 ` Philip Oakley
2015-05-23 9:06 ` Johannes Schindelin [this message]
2015-05-22 13:06 ` Sebastian Schuberth
2015-05-22 13:25 ` Stefan Näwe
2015-05-22 14:17 ` Junio C Hamano
2015-05-22 17:40 ` Philip Oakley
2015-05-22 19:23 ` Stefan Beller
2015-05-22 19:59 ` Johannes Schindelin
2015-05-22 20:04 ` Junio C Hamano
2015-05-22 20:44 ` Stefan Beller
2015-05-23 9:11 ` Johannes Schindelin
2015-05-23 14:29 ` Matthieu Moy
[not found] ` <CAFY1edZ+5fW0FxQPO=qN6gqv8UfQUvjsutKvBOBj0CGbS8ms6A@mail.gmail.com>
2015-05-23 9:09 ` Johannes Schindelin
2015-05-22 16:14 ` Matthieu Moy
2015-05-22 16:27 ` Junio C Hamano
2015-05-22 16:53 ` Stefan Beller
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=696c665281fa2abd35c519e0947fef98@www.dscho.org \
--to=johannes.schindelin@gmx.de \
--cc=Jens.Lehmann@web.de \
--cc=emma@gitforteams.com \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=philipoakley@iee.org \
--cc=rcdailey.lists@gmail.com \
--cc=roberto.tyley@gmail.com \
--cc=sbeller@google.com \
--cc=tfnico@gmail.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.
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).