unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mortimer Cladwell <mbcladwell@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: How to use guix hash --serializer?
Date: Tue, 4 Jan 2022 16:16:24 -0500	[thread overview]
Message-ID: <CAOcxjM4VpcP1hrSuqKvs7r9V=NMjQBsbo44_JXbZ9EoZPOWttw@mail.gmail.com> (raw)
In-Reply-To: <86bl0rcizl.fsf@gmail.com>

Thanks Tobias.
I guess my thinking is that if you have a command line switch like -x that
"excludes version control system directories" it could also exclude empty
directories.
Mortimer

On Tue, Jan 4, 2022 at 4:07 PM zimoun <zimon.toutoune@gmail.com> wrote:

> Hi,
>
> On Tue, 04 Jan 2022 at 15:44, Mortimer Cladwell <mbcladwell@gmail.com>
> wrote:
>
> > looks like the difference, other than make/git related files are four
> empty
> > directories doc, scripts, shinyln and tests, so appears empty directories
> > are not allowed?
>
> “guix hash” hashes all the bytes, not only the bytes tracked by Git.
>
>
> > mbc@HP8300:~/projects/shinyln$  git --no-pager log -1 --oneline
> >   git status
> > 9f06568 (HEAD -> master, origin/master) removed chmod statement
> > On branch master
> > Your branch is up to date with 'origin/master'.
> >
> > nothing to commit, working tree clean
>
> Oh, empty directories is not shown by “git status” and no option to
> display them, if I read correctly.  Ah, I did not known.
>
> Cheers,
> simon
>

  reply	other threads:[~2022-01-04 21:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-04 16:32 How to use guix hash --serializer? Mortimer Cladwell
2022-01-04 16:53 ` zimoun
2022-01-04 19:09   ` Timothy Sample
2022-01-04 19:48     ` Mortimer Cladwell
2022-01-04 19:57       ` Tobias Geerinckx-Rice
2022-01-04 19:58       ` Mortimer Cladwell
2022-01-04 20:17       ` zimoun
2022-01-04 20:44         ` Mortimer Cladwell
2022-01-04 20:57           ` Tobias Geerinckx-Rice
2022-01-04 21:02           ` zimoun
2022-01-04 21:16             ` Mortimer Cladwell [this message]
2022-01-04 20:54     ` zimoun
2022-01-05  1:44       ` Timothy Sample
2022-01-05  7:43         ` zimoun

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='CAOcxjM4VpcP1hrSuqKvs7r9V=NMjQBsbo44_JXbZ9EoZPOWttw@mail.gmail.com' \
    --to=mbcladwell@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=zimon.toutoune@gmail.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.
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).