all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 18237@debbugs.gnu.org
Subject: bug#18237: Small fix for MSDOS
Date: Sun, 10 Aug 2014 22:05:15 +0300	[thread overview]
Message-ID: <83d2c8jhck.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdogqJPL_QoooJRrSQdah-WdGqvKxtmqT9NtbowVuKQW9uQ@mail.gmail.com>

> Date: Sun, 10 Aug 2014 19:42:14 +0100
> From: Reuben Thomas <rrt@sc3d.org>
> Cc: 18237-done@debbugs.gnu.org
> 
> > I'd prefer that all the changes for such a build be committed at once
> > together, not bit by bit, and only if you eventually succeed to
> > produce a working binary using this method.
> 
> Sorry, I was trying to separate my patch into parts with different
> implications (e.g. no effect on the current DOS build system; some effect
> on that system but not more generally; more general changes); but instead
> I'll concentrate on producing a single patch that, as you say, results in a
> working binary.

Yes, I'd prefer that.  This makes it easier to consider all of its
implications at once.  (You can, of course, make separate small
commits on your feature branch, as you work on this; then they will
all be merged onto the trunk as a single merge-commit.)

> I am closing this bug; since you diagnosed my other patch submission as a
> more general bug in configuration, I'll look into a fix for it at that
> level.

Thanks.





      reply	other threads:[~2014-08-10 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-10 16:40 bug#18237: Small fix for MSDOS Reuben Thomas
2014-08-10 18:02 ` Eli Zaretskii
2014-08-10 18:19   ` Reuben Thomas
2014-08-10 18:26     ` Eli Zaretskii
2014-08-10 18:42       ` Reuben Thomas
2014-08-10 19:05         ` Eli Zaretskii [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

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

  git send-email \
    --in-reply-to=83d2c8jhck.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18237@debbugs.gnu.org \
    --cc=rrt@sc3d.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 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.