From: jgart <jgart@dismail.de>
To: Christine Lemmer-Webber <cwebber@dustycloud.org>
Cc: Vagrant Cascadian <vagrant@debian.org>,
Feng Shu <tumashu@163.com>,
Thiago Jung Bauermann <bauermann@kolabnow.com>,
help-guix@gnu.org
Subject: Re: was I hacked?
Date: Thu, 14 Apr 2022 23:08:15 -0400 [thread overview]
Message-ID: <20220414230815.GB22970@gac.attlocal.net> (raw)
In-Reply-To: <87r15zrvvp.fsf@dustycloud.org>
On Thu, 14 Apr 2022 21:11:32 -0400 Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
> It was for you. Since guix pull operates via a git pull, I think it
> should be possible to figure out what the state of the previous branch
> was when the weirdness occured.
Got it. Thanks
> In terms of where to push, you can push to pretty much any forge out
> there. Notabug, Gitlab, etc etc etc.
What I not sure of is what path on my system to find the suspicious
branch/git repo pulled down by `git/guix pull` so I can push it somewhere.
In other words, where does `guix pull` clone the git repo to?
If you know off the top of your head it would be helpful otherwise
I'll find some time to start digging around for it since I've never
explored where exactly guix pull clones the git repo.
I guess somewhere in the /gnu/store/...?
next prev parent reply other threads:[~2022-04-15 3:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 1:28 was I hacked? jgart
2022-04-13 5:25 ` Thiago Jung Bauermann
2022-04-13 21:41 ` jgart
2022-04-14 0:26 ` Feng Shu
2022-04-14 5:17 ` jgart
2022-04-14 16:05 ` Vagrant Cascadian
2022-04-14 20:01 ` jgart
2022-04-14 20:20 ` Christine Lemmer-Webber
2022-04-14 20:27 ` jgart
2022-04-15 1:11 ` Christine Lemmer-Webber
2022-04-15 3:08 ` jgart [this message]
2022-04-15 3:31 ` Jack Hill
2022-04-15 14:05 ` jgart
2022-04-15 17:31 ` jgart
2022-04-15 19:43 ` Edouard Klein
2022-04-15 18:56 ` Christine Lemmer-Webber
2022-04-22 16:47 ` Edouard Klein
2022-04-22 19:58 ` Thiago Jung Bauermann
2022-04-23 15:56 ` Dr. Arne Babenhauserheide
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=20220414230815.GB22970@gac.attlocal.net \
--to=jgart@dismail.de \
--cc=bauermann@kolabnow.com \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=tumashu@163.com \
--cc=vagrant@debian.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/guix.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.