Bug 242512 - Add "git send-email" to Cocoon GUI
Summary: Add "git send-email" to Cocoon GUI
Status: RESOLVED UNMAINTAINED
Alias: None
Product: cocoon
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Riyad Preukschas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-22 19:53 UTC by Johannes Obermayr
Modified: 2018-09-02 22:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Obermayr 2010-06-22 19:53:03 UTC
Version:           unspecified (using Devel) 
OS:                Linux

Since I cannot find a good GUI for Git which supports easy creating of emails via "git send-mail" command Cocoon can contrast strongly.

I assume there could be 3 ways:
1. Use email settings of kmail (preferred)
2. If kmail is not installed/configured: store it in cocoonrc and the password via kwallet (also possible)
3. If kwallet is not installed/used: Store also the password in cocoonrc (but not recommend)

Also configurations for the used repository should be stored (like):

[../kdegames] <-folder on HDD
email=kde-games-devel@kde.org
CC=whatyouwant

[../amarok]
email=amarok-devel@kde.org
CC=whatyouwant

[...]

Reproducible: Always
Comment 1 Riyad Preukschas 2010-06-28 17:26:01 UTC
I have difficulies to think of a concrete example of how this feature is/might be used, as I haven't used it.
Maybe you can explain what you had in mind. It would be nice if you could produce a typical series of commands or outline a use case this feature would be helpful in.
Comment 2 Johannes Obermayr 2010-06-28 18:05:55 UTC
Sorry, the command is "git send-email" ...

1. checkout a repository you do not have permissions for pushing

2. you think something is worth to fix and you fix it

3. your patch should be included upstream - of course, you cannot push

4. with "git send-email" you can send your patch or commit in right and easy way to a mailinglist or a guy with permissions for pushing (may for reviewing)

5. if it gets included then you are the author, the guy who pushed it is the committer


For additional information I found pkqs.net/~sbeyer/tmp/pre-git-clt09.pdf (German) especially page 90 or 68/79 (how you see it).
It describes shortly the feature with a project everyone can push but the elementary things should be also explained.
Comment 3 Riyad Preukschas 2010-06-28 18:56:26 UTC
Ah, ok. Thanks for the explanation. I think I get the picture now.
But please be patient as I'm mainly focused hunting bugs and leaks in the backend right now. But I'll come back to it as soon as the other work is done.
Comment 4 Andrew Crouthamel 2018-09-02 22:06:13 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug.