all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christine Lemmer-Webber <cwebber@dustycloud.org>
To: jgart <jgart@dismail.de>
Cc: Vagrant Cascadian <vagrant@debian.org>, help-guix@gnu.org
Subject: Re: was I hacked?
Date: Thu, 14 Apr 2022 21:11:32 -0400	[thread overview]
Message-ID: <87r15zrvvp.fsf@dustycloud.org> (raw)
In-Reply-To: <20220414162741.GB26758@gac.attlocal.net>

jgart <jgart@dismail.de> writes:

> On Thu, 14 Apr 2022 16:20:05 -0400 Christine Lemmer-Webber <cwebber@dustycloud.org> wrote:
>> It should be possible to use the git reflog to find out what your
>> previous git history state was.
>> 
>> It would be a good idea if you could push the "suspect" branch up
>> somewhere where it can be examined, I'd think?
>
> Hi Christine,
>
> Was that request for me?
>
> If so, how would I push the suspect branch?
>
> All I did was a `git pull`.
>
> Unless you're implying that suspect branch is on my local machine somewhere?
>
> all best,
>
> jgart

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.

In terms of where to push, you can push to pretty much any forge out
there.  Notabug, Gitlab, etc etc etc.

Sorry I don't have time to say more.  Currently sitting in the passenger
seat on a road trip.  I'm not sure if others in the Guix project see
this as a priority, but if you say other users on IRC expereinced
something similar, it may be good to investigate.


  reply	other threads:[~2022-04-15  1:14 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 [this message]
2022-04-15  3:08                   ` jgart
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=87r15zrvvp.fsf@dustycloud.org \
    --to=cwebber@dustycloud.org \
    --cc=help-guix@gnu.org \
    --cc=jgart@dismail.de \
    --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.