| Summary: | Add "git send-email" to Cocoon GUI | ||
|---|---|---|---|
| Product: | [Unmaintained] cocoon | Reporter: | Johannes Obermayr <johannesobermayr> |
| Component: | general | Assignee: | Riyad Preukschas <riyad> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | wishlist | CC: | andrew.crouthamel |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Johannes Obermayr
2010-06-22 19:53:03 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. 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. 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. 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. |