Thanks! בתאריך יום ב׳, 28 בספט׳ 2015, 20:34 מאת Ashish <[email protected]>:
> 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 from scratch. Have I ever lost my > data, yes. But recovered a lot of it from IntelliJ local history. And > sometimes re-wrote the complete solution. I prefer this coz I > precisely know how much I can take and if lot of patches are pending, > I know I have to stop and let the team catch-up. > > It's personal choice, after a few patches you will have your own :) > > On Mon, Sep 28, 2015 at 10:27 AM, IT CTO <[email protected]> wrote: > > 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 sharing! > > Eran > > > > בתאריך יום ב׳, 28 בספט׳ 2015, 20:10 מאת Ashish <[email protected] > >: > > > >> 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 easily. > >> It's a little painful like this, but the simplicity makes my life > >> easy. Since each one is different, helps me to keep track of it. In my > >> case I usually work on lot of JIRA's in parallel. Some are simple and > >> some takes few weeks to get in shape. > >> > >> You can choose whatever works for you. Hope it answers your question. > >> > >> On Mon, Sep 28, 2015 at 9:06 AM, IT CTO <[email protected]> wrote: > >> > 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? > >> > Shouldn't I fork the repo, checkout from my repo so I can save the > >> changes? > >> > > >> > Can someone share his method of work? > >> > Eran > >> > -- > >> > Eran | "You don't need eyes to see, you need vision" (Faithless) > >> > >> > >> > >> -- > >> thanks > >> ashish > >> > >> Blog: http://www.ashishpaliwal.com/blog > >> My Photo Galleries: http://www.pbase.com/ashishpaliwal > >> > > -- > > Eran | "You don't need eyes to see, you need vision" (Faithless) > > > > -- > thanks > ashish > > Blog: http://www.ashishpaliwal.com/blog > My Photo Galleries: http://www.pbase.com/ashishpaliwal > -- Eran | "You don't need eyes to see, you need vision" (Faithless)
