Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0E420200C10 for ; Fri, 3 Feb 2017 20:19:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0B489160B43; Fri, 3 Feb 2017 19:19:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 55A9D160B3F for ; Fri, 3 Feb 2017 20:19:08 +0100 (CET) Received: (qmail 2637 invoked by uid 500); 3 Feb 2017 19:19:07 -0000 Mailing-List: contact dev-help@struts.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Struts Developers List" Reply-To: "Struts Developers List" Delivered-To: mailing list dev@struts.apache.org Received: (qmail 2626 invoked by uid 99); 3 Feb 2017 19:19:07 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2017 19:19:07 +0000 Received: from mail-yw0-f170.google.com (mail-yw0-f170.google.com [209.85.161.170]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 217DB1A002B for ; Fri, 3 Feb 2017 19:19:07 +0000 (UTC) Received: by mail-yw0-f170.google.com with SMTP id v200so17861747ywc.3 for ; Fri, 03 Feb 2017 11:19:07 -0800 (PST) X-Gm-Message-State: AIkVDXJVpDWzbkkT5NAzzOIxf0ezel/tbUKdgPG3ioh5UhsA9zDtJUlXLzkjPdjpO1MsHUT4id16VoLcTlyL/g== X-Received: by 10.13.217.79 with SMTP id b76mr10762103ywe.93.1486149546254; Fri, 03 Feb 2017 11:19:06 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.113.133 with HTTP; Fri, 3 Feb 2017 11:19:05 -0800 (PST) In-Reply-To: References: <30cdc912-7e14-278f-9582-29d6ba4c9eff@apache.org>

From: Stefaan Dutry Date: Fri, 3 Feb 2017 20:19:05 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Documentation To: Struts Developers List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable archived-at: Fri, 03 Feb 2017 19:19:09 -0000 Personaly i can understand everything in there. However i tend to do things differently myself. How i usualy work: * I use clone with https way 1. Fork the repository to my own account 2. clone the repository localy, making my fork 'origin' (git clone ) 3. add the original repository as a remote with the name upstream (git remote add https://github.com/apache/struts.git) 4. create a branch for changes 5. do changes localy 6. add changed files (git add ) 7. commit changes localy (git commit -m "my comment explaining what chang= ed") 8. push to origin (being my fork) (git push origin ) 9. create pull request Reasons for using own fork as origin: * When looking up commands i tend to always come across commands that push to origin * It tends to make it more awkward to accidently try to push to the original git repo Spotted typo: Do you changes and commit them... =3D> Do your changes and commit them ... I'm not saying either way is better, just thought i'd mention this slightly different approach. Regards, Stefaan Dutry (sdutry) 2017-02-03 16:15 GMT+01:00 Lukasz Lenart : > 2017-02-03 16:06 GMT+01:00 Greg Huber : >> How would one resync the github fork with the struts orignal version? > > You don't have to :) You are always starting off the master from origin > > > Regards > -- > =C5=81ukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org > For additional commands, e-mail: dev-help@struts.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org For additional commands, e-mail: dev-help@struts.apache.org