public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Quilt: Unsupported version of git (2.13.2)
Date: Mon, 07 Aug 2017 14:44:00 -0000	[thread overview]
Message-ID: <86shh3v3oi.fsf@gavenkoa.example.com> (raw)
In-Reply-To: <86shh8vh6l.fsf@gavenkoa.example.com>

On 2017-08-03, Oleksandr Gavenko wrote:

> bash# guilt list
> Unsupported version of git (2.13.2)
>
> bash# cygcheck.exe -c -d | grep git'\|'guilt
> 37:git                                   2.13.2-2
> 42:guilt                                 0.35-2

I tried to work with quilt (sorry for typo in subject). So far I have no any
blocking issue with this package.

The only annoying thing is necessity to add files before starting to make
changes. Guilt shouldn't have such issue. At lease Mercurial Queue understands
what is changed in working set despite series of already applied patches.

Sometime it is possible to avoid "quilt add" by importing patch:

  $ git diff >.diff
  $ quilt import -P fix.patch .diff
  $ rm .diff
  $ git reset
  $ quilt push

In Guilt I expect it would be a single command (or two "new" and "refresh").

My ~/.quiltrc:

  QUILT_DIFF_ARGS="--color=auto -p ab"
  QUILT_DIFF_OPTS="-p"
  QUILT_REFRESH_ARGS="-p ab"
  QUILT_PUSH_ARGS="--color=auto"
  QUILT_SERIES_ARGS="--color=auto"

  QUILT_NO_DIFF_INDEX=1
  QUILT_NO_DIFF_TIMESTAMPS=1

-- 
http://defun.work/


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      parent reply	other threads:[~2017-08-07 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-03 14:51 Oleksandr Gavenko
2017-08-07 10:15 ` FAO Jari Aalto: Update guilt package request [Was: Quilt: Unsupported version of git (2.13.2)] Adam Dinwoodie
2017-08-07 10:42   ` Corinna Vinschen
2017-08-07 14:44 ` Oleksandr Gavenko [this message]

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=86shh3v3oi.fsf@gavenkoa.example.com \
    --to=gavenkoa@gmail.com \
    --cc=cygwin@cygwin.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).