unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: brandelune@gmail.com, emacs-devel@gnu.org
Subject: Re: casual contributing with git
Date: Fri, 24 May 2019 19:05:50 +0200	[thread overview]
Message-ID: <87mujb2369.fsf@mbork.pl> (raw)
In-Reply-To: <83lfyz837g.fsf@gnu.org>


On 2019-05-22, at 07:31, Eli Zaretskii <eliz@gnu.org> wrote:

>> From: Marcin Borkowski <mbork@mbork.pl>
>> Date: Sun, 19 May 2019 06:48:25 +0200
>> Cc: Emacs developers <emacs-devel@gnu.org>
>> 
>> 
>> On 2019-05-19, at 03:41, Jean-Christophe Helary <brandelune@gmail.com> wrote:
>> 
>> >> On Jul 5, 2017, at 2:51, Stephen Leake <stephen_leake@stephe-leake.org> wrote:
>> >>
>> >> Workspaces are cheap; I keep a full checkout of master, and one of each
>> >> branch I'm working on, at all times.
>> >
>> > Is that the recommended way ?
>> 
>> Of course not!  (At least, not as far as Git goes in general - but
>> I don't think there is some Emacs idiosyncrasy here.)
>
> In a way, there is: the branches in Emacs tend to diverge very
> quickly, so after a while, if you switch branches in the same tree,
> the builds become very long, and worse: you need to bootstrap each
> time to avoid problems in the built Emacs.  It quickly becomes very
> inconvenient.

Thanks for the info, good to know!

Best,

-- 
Marcin Borkowski
http://mbork.pl



      reply	other threads:[~2019-05-24 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-19  1:41 casual contributing with git Jean-Christophe Helary
2019-05-19  2:08 ` Amin Bandali
2019-05-19  2:30   ` Jean-Christophe Helary
2019-05-20  4:23     ` Amin Bandali
2019-05-19  4:48 ` Marcin Borkowski
2019-05-22  5:31   ` Eli Zaretskii
2019-05-24 17:05     ` Marcin Borkowski [this message]

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mujb2369.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=brandelune@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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.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).