linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 213081] usb-storage / uas Genesys Logic Card Reader no longer working on 5.12
Date: Tue, 18 May 2021 17:57:48 +0000	[thread overview]
Message-ID: <bug-213081-208809-FQbIHk1k4Q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213081-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=213081

--- Comment #12 from Alan Stern (stern@rowland.harvard.edu) ---
In the failed reversion attempt above, what commit was checked out when you
made the attempt?

The right way to do this is to check out the commit and then do the reversion. 
In other words, the commit you want to revert should be the top one at the time
you do the reversion.  This is more or less equivalent to checking out the
commit's parent.

So for example, you should do:

   git checkout 674f8438c121
   git revert 674f8438c121

That way there won't be any conflicts, and the fact that the commit is in the
middle of a larger series won't matter.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-05-18 17:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 12:43 [Bug 213081] New: usb-storage / uas Genesys Logic Card Reader no longer working on 5.12 bugzilla-daemon
2021-05-15 15:36 ` [Bug 213081] " bugzilla-daemon
2021-05-15 17:44 ` bugzilla-daemon
2021-05-15 17:44 ` bugzilla-daemon
2021-05-15 17:45 ` bugzilla-daemon
2021-05-15 17:51 ` bugzilla-daemon
2021-05-16  1:20 ` bugzilla-daemon
2021-05-16  9:51 ` bugzilla-daemon
2021-05-16 15:01 ` bugzilla-daemon
2021-05-17 19:15 ` bugzilla-daemon
2021-05-18  1:47 ` bugzilla-daemon
2021-05-18 16:59 ` bugzilla-daemon
2021-05-18 17:57 ` bugzilla-daemon [this message]
2021-05-18 19:01 ` bugzilla-daemon
2021-05-18 19:48 ` bugzilla-daemon
2021-05-18 21:19 ` bugzilla-daemon
2021-05-19 12:13 ` bugzilla-daemon
2021-05-19 17:31 ` bugzilla-daemon
2021-05-19 17:38 ` bugzilla-daemon
2021-05-19 17:59 ` bugzilla-daemon
2021-05-19 20:12 ` bugzilla-daemon
2021-05-19 21:24 ` bugzilla-daemon
2021-05-19 21:26 ` bugzilla-daemon
2021-05-20 20:04 ` bugzilla-daemon
2021-05-20 21:04 ` bugzilla-daemon
2021-05-21 16:54 ` bugzilla-daemon
2021-05-21 17:01 ` bugzilla-daemon
2021-05-21 19:25 ` bugzilla-daemon
2021-05-21 20:39 ` bugzilla-daemon
2021-05-21 21:56 ` bugzilla-daemon
2021-06-05  7:29 ` bugzilla-daemon

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=bug-213081-208809-FQbIHk1k4Q@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.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.
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 NNTP newsgroup(s).