all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, perry@piermont.com
Subject: Re: minor bzr->git changes missed
Date: Fri, 14 Nov 2014 07:42:56 +0200	[thread overview]
Message-ID: <838ujejq1r.fsf@gnu.org> (raw)
In-Reply-To: <m3r3x6g410.fsf@stories.gnus.org>

> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: "Perry E. Metzger" <perry@piermont.com>,  eggert@cs.ucla.edu,  emacs-devel@gnu.org
> Date: Thu, 13 Nov 2014 22:54:35 +0100
> MailScanner-NULL-Check: 1416520475.64046@ljevEl7WkIEO5ZseDB61fA
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> For reference, is there a description of the full development
> >> process, updated for the git world, one can read?
> >
> > Yes, admin/notes/repo and admin/notes/commits.
> 
> I scanned this and I scanned Git for Emacs Devs, but I'm still not sure
> how to push stuff to the emacs-24 branch.
> 
> Could someone please just write recipe on how to do this, starting with
> 
> git clone --local emacs emacs-24

AFAIU, by using "clone --local", you defined a personalized workflow
that is not what the Wiki describes.  The Wiki describes the situation
where you have a repository cloned from the remote.  Then you just
"git checkout" the branch, make your changes, commit them, and push
them.  Exactly like you do with master, with the addition of the
checkout step.

It's unreasonable to expect the related documentation to describe
every possible personal workflow out there.  If you use your own
workflow, you are expected to know how, or google, or ask specific
questions.



  reply	other threads:[~2014-11-14  5:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 16:00 minor bzr->git changes missed Perry E. Metzger
2014-11-13 16:21 ` Eli Zaretskii
2014-11-13 16:37   ` Perry E. Metzger
2014-11-13 17:16     ` Eli Zaretskii
2014-11-13 17:18       ` Paul Eggert
2014-11-13 17:36         ` Eli Zaretskii
2014-11-13 17:44           ` Perry E. Metzger
2014-11-13 18:08             ` Eli Zaretskii
2014-11-13 18:14               ` Perry E. Metzger
2014-11-13 18:37                 ` Eli Zaretskii
2014-11-13 19:11                   ` Perry E. Metzger
2014-11-13 19:20                     ` Eli Zaretskii
2014-11-13 21:54               ` Lars Magne Ingebrigtsen
2014-11-14  5:42                 ` Eli Zaretskii [this message]
2014-11-14  7:10                 ` Achim Gratz
2014-11-14  7:36                   ` H. Dieter Wilhelm
2014-11-13 17:56           ` Paul Eggert
2014-11-13 18:01             ` Eli Zaretskii
2014-11-13 20:40               ` Paul Eggert
2014-11-14  5:20                 ` Eli Zaretskii
2014-11-13 17:40         ` Perry E. Metzger
2014-11-13 17:36 ` Eric S. Raymond

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=838ujejq1r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=perry@piermont.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.