unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Pavel Shlyak <p.shlyak@pantherx.org>
Cc: 55662@debbugs.gnu.org
Subject: [bug#55662] [PATCH] Ignore temporary files created my macOS
Date: Thu, 26 May 2022 23:09:01 +0200	[thread overview]
Message-ID: <b1dfe2c4fd235ff3debfd185fc27e8c3c977da80.camel@gmail.com> (raw)
In-Reply-To: <F9E2060E-C9D6-4804-8B90-FDF0DE4C414F@pantherx.org>

Am Donnerstag, dem 26.05.2022 um 23:24 +0300 schrieb Pavel Shlyak:
> I hope so!
> 
> > 26 мая 2022 г., в 22:33, Liliana Marie Prikler
> > <liliana.prikler@gmail.com> написал(а):
> > 
> > Am Donnerstag, dem 26.05.2022 um 20:34 +0300 schrieb Pavel Shlyak:
> > > Check https://en.wikipedia.org/wiki/.DS_Store and
> > > https://stackoverflow.com/questions/107701/how-can-i-remove-ds-store-files-from-a-git-repository
> > >  for more details
> > Is there a realistic chance that anyone working on Guix will ever
> > commit this to upstream?  Note that you can set up a global
> > gitignore, e.g. under $XDG_CONFIG_HOME/git/ignore on Linux distros
> > such as Guix System.
Pardon my lack of clarity.  By "this" I meant a file that's exclusively
produced by a proprietary operating system for no good reason (the
.DS_Store).  I don't think any of our committers run a risk of
accidentally pushing it, do they?




  reply	other threads:[~2022-05-26 21:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-26 17:34 [bug#55662] [PATCH] Ignore temporary files created my macOS Pavel Shlyak
2022-05-26 19:33 ` Liliana Marie Prikler
2022-05-26 20:24   ` Pavel Shlyak
2022-05-26 21:09     ` Liliana Marie Prikler [this message]
2022-05-26 21:43       ` Maxime Devos
2022-05-26 21:07   ` Maxime Devos
2022-05-26 21:09     ` Pavel Shlyak
2022-06-05 19:07 ` bug#55662: " Mathieu Othacehe

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=b1dfe2c4fd235ff3debfd185fc27e8c3c977da80.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=55662@debbugs.gnu.org \
    --cc=p.shlyak@pantherx.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/guix.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).