From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Contributing Without Patches ...
Date: Sat, 14 Sep 2013 20:12:57 +0200 [thread overview]
Message-ID: <8761u3clw6.fsf@Rainer.invalid> (raw)
In-Reply-To: 20130914172240.GJ28088@kuru.dyndns-at-home.com
Suvayu Ali writes:
> On Sat, Sep 14, 2013 at 09:45:47AM -0600, Eric Schulte wrote:
>> Pull requests are a github thing, not a git thing.
>
> Well actually I think it is a Git thing. I believe it just says: my
> changes are in the public branch <some_url>, kindly pull from there;
> eliminating the need to attach patches. As an added advantage, it
> preserves the commit hashes and many other committer/author information.
That requires that the repository in question is configured as a remote,
so you aren't usually in a position to tell upstream to pull from your
repository (it only ever gets pushed to). The "Github thing" with the
pull request is that you can make a feature branch to any repo and then
ask the maintainer to pull from there, which merges your changes.
There is no author information lost when you send patches as long as
they are created by format-patch. As with any rebase, the history is
thrown away, but that is mostly a good thing for patches.
> As far as I have seen, many projects work this way: Linux kernel, Git.
Linux kernel works via mail, just like Orgmode.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2013-09-14 18:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 23:42 Contributing Without Patches aditya siram
2013-09-14 0:27 ` Suvayu Ali
2013-09-14 13:14 ` aditya siram
2013-09-14 14:23 ` Suvayu Ali
2013-09-14 15:45 ` Eric Schulte
2013-09-14 17:22 ` Suvayu Ali
2013-09-14 18:12 ` Achim Gratz [this message]
2013-09-14 18:52 ` Suvayu Ali
2013-09-14 20:09 ` Achim Gratz
2013-09-14 21:58 ` Suvayu Ali
2013-09-15 2:10 ` Samuel Wales
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: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8761u3clw6.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).