Thanks!
בתאריך יום ב׳, 28 בספט׳ 2015, 20:34 מאת Ashish :
> If you have the patch file uploaded, you can download and apply it to
> get your working version.
> Rebase is simple, git pull.
>
> If the patch is large I prefer to take a backup. But most part not
> worried much about it. Once I know ho
If you have the patch file uploaded, you can download and apply it to
get your working version.
Rebase is simple, git pull.
If the patch is large I prefer to take a backup. But most part not
worried much about it. Once I know how to solve the JIRA, its mostly
easy to recreate the solution even fro
Thanks for the reply.
So you build a local repo for every jira issue you work on... this make
sence but force you to rebase frequently especially if you update the doc
file which is one big file...
Also, in this scenario you don't have a backup on cloud for your source,
right?
Again, thanks for s
Flume doesn't accept PR's so fork or not is your choice.
Simplest workflow could be
keep an updated clone of repo
Make the changes
Create a patch and upload to JIRA
I think your main concern is how to manage locally. I prefer to keep
clone's specific to JIRA's which help me in tracking them easil
Hi,
I read the
https://cwiki.apache.org/confluence/display/FLUME/Developers+Quick+Hack+Sheet
If I write my code where my origin is the
origin https://github.com/apache/flume.git (fetch)
origin https://github.com/apache/flume.git (push)
How can I save my changes while they are being reviewed?
Shoul
