unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: pipcet@protonmail.com
Cc: emacs-devel@gnu.org,  "Richard M. Stallman" <rms@gnu.org>
Subject: Re: master 18491f48d97: Install cond*
Date: Sun, 11 Aug 2024 17:39:21 +0200	[thread overview]
Message-ID: <m2ikw7qdau.fsf@macmutant.fritz.box> (raw)
In-Reply-To: <87sevb3zfi.fsf@protonmail.com> (pipcet@protonmail.com's message of "Sun, 11 Aug 2024 14:30:03 +0000")

pipcet@protonmail.com writes:

> "Richard M. Stallman" <rms@gnu.org> writes:
>
>> branch: master
>> commit 18491f48d973c9cbc453d9f742ec7f73e83df3bb
>> Author: Richard Stallman <rms@gnu.org>
>> Commit: Richard Stallman <rms@gnu.org>
>>
>>     Install cond*
>>
>>     * oond-star.el: New file.
>
> Would it be okay if I ran whitespace-cleanup on that file? It would make
> working with our git pre-commit hooks easier when merging into other
> branches, even though I know that cosmetic changes are usually
> discouraged. Could we make an exception for this one?

I suggest to have a look at bug#72546.  It provides a lot of cleanup,
including the whitespace issue.

Best, Arash



  reply	other threads:[~2024-08-11 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <172261466172.7510.6915341032301910893@vcs2.savannah.gnu.org>
     [not found] ` <20240802160422.677A8C1CAF8@vcs2.savannah.gnu.org>
2024-08-11 14:30   ` master 18491f48d97: Install cond* pipcet
2024-08-11 15:39     ` Arash Esbati [this message]
2024-08-11 15:49     ` Eli Zaretskii
2024-08-11 16:11       ` Pip Cet
2024-08-11 17:51         ` Eli Zaretskii

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=m2ikw7qdau.fsf@macmutant.fritz.box \
    --to=arash@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pipcet@protonmail.com \
    --cc=rms@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).