From: Stephen Berman <stephen.berman@gmx.net>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org, Yuri Khan <yuri.v.khan@gmail.com>
Subject: Re: git commit/push and VC
Date: Thu, 20 Nov 2014 13:28:37 +0100 [thread overview]
Message-ID: <877fyqt5sa.fsf@rosalinde.fritz.box> (raw)
In-Reply-To: <mg8uj6sjzn.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 19 Nov 2014 21:07:08 -0500")
On Wed, 19 Nov 2014 21:07:08 -0500 Glenn Morris <rgm@gnu.org> wrote:
> Stephen Berman wrote:
>
>> possible to use VC to push changes to another branch or repository, and
>> if so, how?
>
> `vc-pull' exists, but nobody wrote (or nobody pushed, ha ha) `vc-push'.
>
> Eg
> http://debbugs.gnu.org/12415
> http://lists.gnu.org/archive/html/emacs-devel/2009-12/msg00267.html
> http://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00842.html
On Thu, 20 Nov 2014 10:29:30 +0700 Yuri Khan <yuri.v.khan@gmail.com> wrote:
> On Thu, Nov 20, 2014 at 5:36 AM, Stephen Berman <stephen.berman@gmx.net> wrote:
>
>> GitForEmacsDevs says this:
>>
>> If you are a committer, you can merge to the upstream master directly.
>>
>> First, update your repository:
>>
>> cd $DEVHOME/emacs
>> git checkout master
>> git pull
>> git merge TASKNAME
>> git push
>>
>> Run the tests:
>>
>> make check
>>
>> and then commit
>>
>> git status
>> git commit -m "fixes debbugs:12345"
>>
>> which merges all your new commits to the upstream master.
>>
>> I don't understand why `git commit' follows `git push' here (or why
>> there isn't another `git push' after `git commit').
>
> Indeed, the instruction quoted above is strange.
[...]
Thanks to both of you for the replies. I see that GitForEmacsDevs on
the Wiki has been updated in the mean time, so it's clearer (and
hopefully correct) now.
Steve Berman
next prev parent reply other threads:[~2014-11-20 12:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 23:36 git commit/push and VC Stephen Berman
2014-11-20 2:07 ` Glenn Morris
2014-11-20 12:28 ` Stephen Berman [this message]
2014-11-20 3:29 ` Yuri Khan
2014-11-20 15:45 ` Eli Zaretskii
2014-11-20 18:17 ` Achim Gratz
2014-11-20 20:59 ` Eli Zaretskii
2014-11-21 0:31 ` Stephen J. Turnbull
2014-11-21 9:01 ` Eli Zaretskii
2014-11-22 5:30 ` Stephen J. Turnbull
2014-11-22 5:50 ` Yuri Khan
2014-11-22 7:17 ` Stephen J. Turnbull
2014-11-22 6:50 ` Ivan Shmakov
2014-11-22 7:25 ` Stephen J. Turnbull
2014-11-22 7:42 ` Ivan Shmakov
2014-11-22 8:59 ` Stephen J. Turnbull
2014-11-22 8:36 ` Eli Zaretskii
2014-11-22 8:37 ` Andreas Schwab
2014-11-22 8:50 ` Ivan Shmakov
2014-11-22 8:35 ` Eli Zaretskii
2014-11-22 9:36 ` Stephen J. Turnbull
2014-11-22 10:25 ` Eli Zaretskii
2014-11-22 11:31 ` Andreas Schwab
2014-11-22 12:37 ` Eli Zaretskii
2014-11-22 13:00 ` Andreas Schwab
2014-11-22 13:45 ` Eli Zaretskii
2014-11-22 14:12 ` Andreas Schwab
2014-11-22 15:20 ` Eli Zaretskii
2014-11-21 8:23 ` martin rudalics
2014-11-21 9:06 ` Eli Zaretskii
2014-11-21 9:40 ` Dani Moncayo
2014-11-21 10:24 ` martin rudalics
2014-11-21 10:40 ` Eli Zaretskii
2014-11-21 8:49 ` Thien-Thi Nguyen
2014-11-21 9:12 ` Eli Zaretskii
2014-11-22 10:30 ` Eli Zaretskii
2014-11-22 10:43 ` David Kastrup
2014-11-22 11:01 ` Eli Zaretskii
2014-11-22 11:16 ` Eli Zaretskii
2014-11-22 11:22 ` David Kastrup
2014-11-21 10:34 ` Stephen Berman
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=877fyqt5sa.fsf@rosalinde.fritz.box \
--to=stephen.berman@gmx.net \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=yuri.v.khan@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.