| www.delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
| X-Recipient: | geda-user AT delorie DOT com |
| Message-ID: | <50968094.9080603@xs4all.nl> |
| Date: | Sun, 04 Nov 2012 15:49:56 +0100 |
| From: | Bert Timmerman <bert DOT timmerman AT xs4all DOT nl> |
| User-Agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.19) Gecko/20110429 Fedora/2.0.14-1.fc13 SeaMonkey/2.0.14 |
| MIME-Version: | 1.0 |
| To: | geda-user AT delorie DOT com |
| Subject: | Re: [geda-user] The state of gEDA/gaf (Was gEDA/PCBs diversity, Was: |
| Pin hole size) | |
| References: | <CANqhZFxYH+Y5U1ai7ey-s+4nz6eYDM2vx3aMDb7WuigNXmi4AQ AT mail DOT gmail DOT com> <1511E63C-F435-44B1-9734-C7AF7AF49A92 AT sbcglobal DOT net> <20121030132922 DOT GY32696 AT fi DOT muni DOT cz> <201210312340 DOT q9VNe3VW012697 AT envy DOT delorie DOT com> <CAC4O8c-xvCH8j2h3K3+ymO0Zgbru_JqDavqojY81iT_C=-zPrw AT mail DOT gmail DOT com> <CAGde_xOu96b1jxN1n2km3_OAkX9umshs9FQF+Gdjgsbw_Mt4qQ AT mail DOT gmail DOT com> <CAC4O8c8BiPJSJyvTDs337ix2e==+bLwzz3TgqD8rV+B4TPkSxw AT mail DOT gmail DOT com> <50964B74 DOT 9040205 AT jump-ing DOT de> |
| In-Reply-To: | <50964B74.9040205@jump-ing.de> |
| X-Virus-Scanned: | by XS4ALL Virus Scanner |
| X-MIME-Autoconverted: | from 8bit to quoted-printable by smtp-vbr5.xs4all.nl id qA4Env5h025791 |
| X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id qA4Eo7d4022121 |
| Reply-To: | geda-user AT delorie DOT com |
Markus Hitter wrote:
> Am 03.11.2012 23:10, schrieb Britton Kerin:
>> I think this page replaces most of it:
>>
>> http://www.kernel.org/pub/software/scm/git/docs/everyday.html
>
> I had more success with Wine's Git descriptions:
>
> http://wiki.winehq.org/GitWine#head-20352a9b6bbab91763387de5b12a36a9fecc87b0
>
>
> Also, I think this "sending patches" mechanism they ask for would be a
> nice fit for the casual gEDA developer. Doing so is straightforward:
>
> 1 - Commit the change(s) in as many commits you see fit in your local
> repo. In doubt, more commits with smaller changes in each are better.
>
> 2 - Do a git format-patch --keep-subject origin/master
>
> 3 - You'll get numbered file(s), starting with 0001-... Send them to
> this list as-is or - even better - open a bug on Launchpad and attach
> them there. They'll be easy to apply.
>
>
> - - -
>
> Also, gitk is IMHO worth a few words of mentioning. Simple to install
> and use and helps greatly keeping the overview over what happens in
> the repo. Just do a menu -> file -> reload before and after every action.
>
>
> my $0.02
> Markus
>
Hi Markus,
I happen to use the git-gui and qgit a lot ("qgit --all &" from the
CLI), the latter has built-in functions for applying and creating
git-patches ("git format-patch").
Qgit comes with user configurable actions:
<quote>
Actions can be added/removed using a dedicated dialog invoked from
Actions→Setup actions… menu. Actions can be activated clicking on their
name from the Actions menu.
Each action can be associated to a list of any type of git or shell
commands or to an external script.
While an action is running a terminal window is shown to display the
corresponding output.
An action can also ask for command line arguments before to run so to
allow for maximum flexibility.
</quote>
I use this for calling frequently used functions.
Qgit also has StGit integration.
Kind regards,
Bert Timmerman.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |